home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 2.1 KB | 55 lines | [TEXT/GEOL] |
- Item forwarded by YEPEZ1 to SOLVIK
-
- Item 7897493 7-Aug-89 14:50
-
- From: BURBECK.S Burbeck, Steve
-
- To: KNEPPER Knepper, Christopher
-
- cc: MACAPP.CUP$ MacApp Interest List - Cupertino
-
- Sub: re building blocks
-
- Chris,
-
- All of your questions are good ones that need discussion. So let me open the
- discussion by offering my view.
-
- • What forum for building block code review will be provided? I suggest at
- minimum that a review committee be formed consisting of members from MacDTS,
- the MacApp engr team, SQA (PQS?), etc.
-
- A review committee would be very valuable, both in spreading the work load
- and in getting a wide range of viewpoints.
-
- • What assumptions, if any, may be made in the building blocks we develop?...
-
- One of the hallmarks of reusable building blocks is careful elimination of
- arbitrary assumptions. If you have a solid reason to insist that users of your
- TView subclasses may not create them procedurally, no problem. Otherwise users
- who prefer procedural creation will be irate.
-
- • What distribution channels will be provided? MADA? APDA?
-
- The primary channel would be APDA. Different kinds of building block
- probably warrant different distribution. Those that will be very widely useful
- probably should be incorporated into MacApp itself; more specialized ones may
- make more sense as separate APDA products.
-
- • What testing will be done on these classes we provide? Will SQA allocate
- resources to test classes contributed to this building block library?
-
- I can't speak for SQA, but reusable building blocks will need as careful
- testing as MacApp itself. If we are to distribute them as Apple products, we
- must test them and SQA must OK them. We may be able to leverage off of other
- efforts within Apple. For instance Alberto Yepez is already looking at buiding
- block issues within IS&T.
-
- • What about licensing...
-
- Since building blocks are source code, we would probably handle licensing
- much as we do with MacApp itself.
-
- Steve
-
-